Skip to content

docs: fix Supabase Storage example anchor links - #4510

Draft
Rohan170603 wants to merge 1 commit into
triggerdotdev:mainfrom
Rohan170603:docs/fix-supabase-storage-anchor-links
Draft

docs: fix Supabase Storage example anchor links#4510
Rohan170603 wants to merge 1 commit into
triggerdotdev:mainfrom
Rohan170603:docs/fix-supabase-storage-anchor-links

Conversation

@Rohan170603

@Rohan170603 Rohan170603 commented Aug 5, 2026

Copy link
Copy Markdown

✅ Checklist

  • I have followed every step in the contributing guide
  • The PR title follows the convention.
  • I ran and tested the code works.

Testing

  • Ran the documentation site locally.
  • Verified that both links in the Overview section navigate to the correct sections of the page.
  • Ran npm run lint (only an existing unrelated warning was reported).

Changelog

Updated the Overview links in the Supabase Storage upload guide to use the current heading anchors instead of outdated fragment identifiers. This fixes navigation to both example sections.

Screenshots

N/A (documentation-only change)

@changeset-bot

changeset-bot Bot commented Aug 5, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 29e366e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai

coderabbitai Bot commented Aug 5, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: fbfb571c-7a5a-4c72-8f2d-846cd0577eb3

📥 Commits

Reviewing files that changed from the base of the PR and between c01a4f1 and 29e366e.

📒 Files selected for processing (1)
  • docs/guides/examples/supabase-storage-upload.mdx
📜 Recent review details
🧰 Additional context used
📓 Path-based instructions (1)
docs/**/*.mdx

📄 CodeRabbit inference engine (docs/CLAUDE.md)

docs/**/*.mdx: MDX documentation pages must include frontmatter with title (required), description (required), and sidebarTitle (optional) in YAML format
Use Mintlify components for structured content: , , , , , , /, /
Always import from @trigger.dev/sdk in code examples (never from @trigger.dev/sdk/v3)
Code examples must be complete and runnable where possible
Use language tags in code fences: typescript, bash, json

Documentation in docs/ uses MDX conventions defined by the documentation guidance.

Files:

  • docs/guides/examples/supabase-storage-upload.mdx
🧠 Learnings (2)
📚 Learning: 2026-03-10T12:44:14.176Z 
Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 3200
File: docs/config/config-file.mdx:353-368
Timestamp: 2026-03-10T12:44:14.176Z
Learning: In the trigger.dev repo, docs PRs are often companions to implementation PRs. When reviewing docs PRs (MDX files under docs/), check the PR description for any companion/related PR references and verify that the documented features exist in those companion PRs before flagging missing implementations. This ensures docs stay in sync with code changes across related PRs.

Applied to files:

  • docs/guides/examples/supabase-storage-upload.mdx
📚 Learning: 2026-04-30T20:30:29.458Z 
Learnt from: ericallam
Repo: triggerdotdev/trigger.dev PR: 3226
File: docs/ai-chat/quick-start.mdx:13-13
Timestamp: 2026-04-30T20:30:29.458Z
Learning: In this repo’s documentation MDX files (`docs/**/*.mdx`), use `ts` and `tsx` (not `typescript`) as the code-fence language tags for TypeScript/TSX snippets. Do not flag `ts`/`tsx` code-fence language tags as incorrect in any docs MDX file, since this is the site-wide Mintlify-compatible convention.

Applied to files:

  • docs/guides/examples/supabase-storage-upload.mdx
🔇 Additional comments (1)
docs/guides/examples/supabase-storage-upload.mdx (1)

14-15: LGTM!

Walkthrough

The Supabase storage upload guide updates two table-of-contents links. The links now use local fragment anchors for the Supabase and AWS S3 upload sections instead of absolute guide URLs.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the documentation change and the corrected Supabase Storage anchor links.
Description check ✅ Passed The description covers testing, changelog, screenshots, and checklist requirements, but it omits the optional issue closure line.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Rohan170603